QRZ! Ham Radio 5/QRZ Ham Radio Callsign Database - Volume 5.iso/files/tcpip/hrlnos/minihrl.doc

Text File | 1994-11-27 | 24.8 KB | 642 lines

Changes in HRLNOS/MINIHRL compared to NOS PA0GRI 910816

by R. Kolb PA3EUG [e-mail]; PA3EUG @ ON4UBO;
   [e-mail]
For HRLNOS/MINIHRL releases around mar 19, 1992.
(p) PA3EUG 920319.

Differences between HRLNOS and MINIHRL
HRLNOS and MINIHRL are quite the same, except for the NET/ROM
part. In MINIHRL NET/ROM has been omitted in all OSI layers.
HRLNOS however has full NET/ROM possibilities. Omitting NET/ROM
means that about 80 kbytes more core memory is available. Any
limits in possibilities in HRLNOS/MINIHRL are due to memory
limits.
HRLNOS/MINIHRL guaranties full compatibility to the standards as
adapted in the original KA9Q/NOS versions. Any "hacking" in the
respective servers has been avoid.

StartUp File
To make sure that HRLNOS and MINIHRL would be installable in the
same directory, there are different names issued to the
respective autoexec files.
HRLNOS has a default autoexec file named "autoexec.nos"
MINIHRL has a default autoexec file named "autoexec.hrl"
These file names are changable in the DOS command line like in
other NOS versions.

AX25 Server
In HRLNOS/MINIHRL the AX25 server has been exchanged to the
WAMPES server. This means that there is AX25 autorouting and AX25
routes are memorized. This has lead to some minor changes,
resulting in some differences for the user. See further down for
more information. Any received packets originating from someone
who's using the same callsign as the call set with the "ax25
mycall" command, are ignored. This is done to prevent any illegal
hacking in the system.

System status line
The top line in the screen gives an impression of the current
connections. First there is the current -local- time, followed by
the name of the software package (HRLNOS/MINIHRL). Then there is
a character stating the window type: T = trace window, C =
command window and * is session window. This is followed by an
entry for every existing session. A session is reported as in
this example:
1:U:R:PA3EUG
First there is the session number. This is followed by a "U" when
Uploading or a R when recording. Last on the entry there is the
name of the session. This may either be a callsign (name in
CAPITALS) when the session is of the AX25 type, or a hostname/IP-
address when the session is of the TCP/IP or UDP/IP type, or a
filename when the session is opened as a result of a "more"
command, or a directory name when the sessions is the result of a
"dir" command. Another special session name is "local bbs" when
it's opened by the "bbs" command, or "chat" when the session is
the result of an incoming chat request.
If the session name is blinking, there has NEW INFORMATION
arrived. It is possible to switch between the sessions with the
function keys F1-F8. F9 and F10 are reserved for switching to the
special windows:
F9 switches to the TRACE window. (BTW: trace will be shown ONLY
as specified by the "trace" command)
F10 switches to the command window.

Timers
Because of "dynamic" timer management several timers have been
removed or changed. For changes in the AX25 area, see the AX25
section. In the IP section, all timing is now dynamic. The TCP
timers are depending on the set frame mode. When sending UI
frames, nothing has changed. When sending I frames (in mode VC,
AUTO or IPCAM) the SRTT is multiplied by 10. The maximal time
before a retry is now about 300 seconds. This has as the next
results:
1. Any unnecessary retries in level 4/5 will be omitted, because
the AX25 "transport" layer has been provided with "intelligent"
Hop-to-Hop-acknowledgement digipeating (FlexNet compatible).
2. Because the RTT has been limited to about 300 sec., after this
time a "lost" AX25 connection will be rebuilt.

Mailbox
The HRLNOS/MINIHRL mailbox has become a new outfit compared to
the KA9Q/NOS mailboxes. For any information see the mailbox help
files which are provided with your HRLNOS/MINIHRL copy. The
KA9Q/NOS bbs documentation is still fully valid! All messages are
now related to the RMNC/Flexnet software messages.
It is possible to set your own mailbox connect text. This text
will be sent from the file /SPOOL/HELP/HOST.HLP. NET/ROM -when
available- has been integrated into the mailbox itself. When the
parameter "ax25 t3disc" has been set "on", a message "Inactivity
time out xxx minutes" will be shown on the screen. The mailbox
prompt may be set with the "mbox mota <mailbox prompt>" command.

Windowing
In the several text windows there are split line possibilities:
When typing text, it will appear on the bottom line of the
screen. The text will remain there until <CR> is typed or the
number of characters set with the "wrap" command is exceeded.
Word editing commands are:
CTRL-U : delete current line
CTRL-W : delete last word
CTRL-R : retype last line before <CR>
CTRL-B : repeat last input
The line buffer contains several lines that are typed, and is
accessable by CTRL-B and the UP/DOWN cursor control keys.


ARP
TCP/IP autorouting is done by maintaining a permanent ARP list.
Whenever a IP based packet is received, the AX25 address and the
incoming subnet type (AX25, NET/ROM etc.) is stored in the ARP
list. This list is saved to the file "ARPROUTE.DAT" everytime the
arp save timer ticks. This timer can be set with the "arp save"
command. Saving only takes place when a new entry is added to the
ARP list. By retaining the interface in which the AX25 part is
received, full autorouting is possible. See the AX25 section for
more information.

attribute
Syntax: attribute <color|mono>
With the attribute command the monitor type can be set. This
changes the behaviour of the status line. Remark: this command
may give an ERROR when used in the autoexec file. HOWEVER, the
command IS performed! So just use in in the autoexec and neglect
the error message....

bell
Syntax: bell <0...9>
Sets the number of bell "beeps" that are issued at an incoming
chat.

connect
Syntax: connect [<iface>] <call> [<digis>]
This command can be used like in other NOS versions. However,
when the route to a callsign is known by the AX25 autorouter, the
interface and the digipeaters can be omitted. E.g. when the
autorouter knows that the route to PI8HRL is via PE1MUL and
PI8EHV, a "c pi8hrl" command will do the same as a "c 144 pi8hrl
pe1mul pi8ehv" command. For more information on the AX25
autorouter see the AX25 section.

domain dfile
Syntax: domain dfile <path>
This command sets the path to the domain file. This makes the use
of domain files in RAMDISKS etc. quite easy.

mbox log
Syntax: mbox log <on|off>
Logs mailbox accesses to the file /spool/node.log.
Default: off

mem efficient
Syntax: mem efficient <0|1>
With mem efficient 1 a more effictive memory management will be
performed. This results into a slower memory allocation, but it
prevents any memory loss!
On slow systems both possibilities should be tried!
Default: 1

mem thresh
Syntax: mem thresh <bytes>
This is the minimum amount of left core memory. When this value
is reached, incoming frames will be ignored or rejected (IP: ICPM
Source Squench). This parameter also influences the number of
calls to the subroutine, responsible for memory reservation.
Default values vary from release to release.

mode
Syntax: mode <iface> [<da/dg|vc|ipcam|auto>]
Mode da(tagram) (or dg) and mode vc are the same as in other NOS
releases.
Mode IPCAM is simular to mode vc, and only differs in the fact,
that the AX25 Pid is set to "Text" instead of "Ip". This makes a
multi-protocol digipeating possible, e.g. over NET/ROM and over
FlexNet.
Mode AUTO means: mode DATAGRAM when using 1 or less AX25
digipeater and mode VC when using more than 1 AX25 digipeater.
Problems may occur when using an existing AX25 connection that is
transfering TEXT for a VC connection too! Data may be lost.

smtp batch
Syntax: smtp batch <0|1>
With smtp batch 1, it is possible to send more than one command
line in a smtp session at a time. So when an smtp session is
established, the commands:
     HELO pa3eug.ampr.org
     MAIL FROM:<[e-mail]>
     RCPT TO:<[e-mail]>
     DATA
will be issued in ONE packet, without waiting for an
acknowledgement. Of course, after the "DATA" command, no text
will be sent until the message "Send mail, end with ." is
received.

Ist "smtp batch 0" wartet der SMTP Client nach dem Aussenden
eines Frames auf die Antwort des Host. Wird "smtp batch" auf 1
gesetzt, werden die notwendigen SMTP Kommandos in moeglichst
wenigen Frames gesendet. Da einige SMTP Server jedoch einen
bestimmten Rhythmus der Kommandos benoetigen, sollte der Wert
dieses Befehls ausprobiert werden.
Default: 0

smtp quiet
Syntax: smtp quiet <0|1>
This parameter is a little bit "upside down". When set to 1,
there will be a "beep" issued when mails are received. When set
to 0, the system will remain silent.
Default: 1

smtp usemx
Syntax: smtp usemx <0|1>
When set to 1, every time a mail is sent the domain file will be
scanned for MX entries. Normally such an entry will be not
available in HAM radio. When this parameter is set to 0, the scan
for a MX entry will be omitted.
Default: 0

sysop
Syntax: sysop <nummer>
This sets the secret password number (5 figures, not 00000) for
remote operation. When someone has an entry as SYSOP in the
/ftpusers file (permission code 127), he may give the command "@"
in the mailbox. This command return 3 groups of 5 figures. The
remote sysop chooses one of the groups, and make this
calculation:
"secret" password number entered with the sysop command: abcde
one of the 5 figures groups in the mailbox: vwxyz
result = a.v+b.w+c.x+d.y+e.z
Now the remote sysop returns the result to the mailbox and -if he
has done everything OK-, he gets remote sysop control.

tcp close
Syntax: tcp close <tcb>
Closes "sleeping" TCP connections in a decent way. Compare with:
TCP reset <tcb>

tcp retry
Syntax: tcp retry <retries>
This command is added to avoid endless retries to build a
connection, especially with SMTP.
The number of retries is specified for those connections that are
not in state "established". Whenever a connection is established,
the retry value will be multiplied by 5.
With tcp retry 0, the number of retries will be endless.
Default: 5

wrap
Syntax: wrap <count>
See windowing section. Wrap 0 will switch wrap off.
Default: 70 - Range: 0 .. 132

write
Syntax: write <socket [socket..]> <text>
Sends a message to the one connected on the stated socket(s).

AX25 behaviour.
Several AX25 commands have been changed or extended and several
commands have been added. For autorouting explanation see the
AX25 route subcommand set. Here are some subcommands:

ax25 bc
Syntax: ax25 bc <iface>
Sends an UI frame containing the text set with "ax25 bct" to ID
on the stated interface.

ax25 bcinterval
Syntax: ax25 bcinterval <sec>
On every tick of this timer, the text set with "ax25 bct" will be
transmitted to ID on all the interfaces. On ax25 bci 0 no
transmissions will be performed.

ax25 bctext
Syntax: ax25 bctext <text>
Sets broadcast text.

ax25 close
Syntax: ax25 close <axcb>
Closes AX25 level 2 connections in a decent way. The connection
is not closed until all frames are confirmed.

ax25 digipeat
Syntax: ax25 digipeat <0|1|2>
Sets the way of digipeating
0 = no digipeating
1 = normal digipeating
2 = Autorouting with Hop-to-Hop-Acknowledgement
Default: 2

ax25 heard
Syntax: ax25 heard [<iface>]
This shows the last 40 stations heard on the stated channel, or,
when the interface is omitted, on all interfaces.

ax25 idigi
Syntax: ax25 idigi <iface> <call>
Sends ALL OUTGOING PACKETS on the respective interface via L2-
digipeater <call>. This command is useable for 2nd systems linked
to the radio connected system via an AXIP link.

ax25 mycall
Syntax: ax25 mycall <call>
This command HAS TO BE ISSUED BEFORE THE ATTACHMENT OF ANY
INTERFACE!

ax25 route
HRLNOS/MINIHRL is provided with an AX25 autorouter. This
autorouter stores EVERY time a connect is performed to or from
your system the path to that station in a table. Every 10 minutes
this table will be saved into the file "axroutes.dat". This file
is recalled every start-up. The first time HRLNOS/MINIHRL is
started, the file will be NOT available. This results in a
message, but don't bother: it will make it for you.
When an entry a certain time not is used (this time can be set
with the "ax25 route save" command), it will be removed from the
table. The entries are stored in a "chain", so the route to every
intermediate station is known too. This is done in accordance to
the "Stuttgart WAMPES project". Erasing of entries is not
possible, but you can change them with the "ax25 route add"
command.

Subcommands: add, list, stat

ax25 route add
Syntax: ax25 route add [permanent] <iface> <"default"|call>
                                                           <digi>
Manual addition of AX25 routes. When stating "permanent",
automatic changes by the autorouter are disabled. The command
"ax25 route add default 144" sets the interface 144 to the
default interface. Every station that is not in the list will be
routed to that particular interface.
The words "permanent" and "default" cannot be abbreviated.
The routings will be stored in a chain. For every respective
route an entry is created. Example:
ax25 route add 144 hb9zz pe1mul pi8ehv pi8hrl hb9eas
This will result in the following additions to the routing table:
     144 hb9zz v pe1mul pi8ehv pi8hrl hb9eas
     144 hb9eas v pe1mul pi8ehv pi8hrl
     144 pi8hrl v pe1mul pi8ehv
     144 pi8ehv v pe1mul
     144 pe1mul
Now, it is possible to reach hb9zz by typing "c hb9zz".

ax25 route list
Syntax: ax25 route list [<call> [<call ...>]]
Lists all ax25 router entries

ax25 route stat
Syntax: ax25 route stat
Returns the number of entries in the router.

ax25 status
Syntax: ax25 status <axcb>
There are some additions to other NOS versions: Also information
about the frame collector is present. When HRLNOS/MINIHRL
receives a frame that has not the expected frame number, it will
keep it in mind and restore it when the lost frame is received.
This is to avoid retransmission of frames that are received
correct, but have a wrong frame sequence. These frame can be
found in "reassembly frames" and "resend frames" entries.

ax25 t1|t2|t3|t4|t5
Syntax: ax25 tx <sec> - with "x" for Timer 1 to 5
Timer 1:  Retransmission timeout
          At tick, a unconfirmed frame will be repeated or a
          RR(P) frame is sent. This timer is dynamic depends on
          the set value, the number of digis, the srt and the
          mdev of the connection.
          default: 10, range 1-15
Timer 2:  Acknowledgement delay timeout
          At tick, incoming frames are confirmed. This is to
          avoid that every incoming frame is confirmed
          seperately. Timer 2 must have a smaller valua than
          timer 5.
          Default: 2, range 1-15
Timer 3:  Link redundancy timer
          On "ax25 t3disc y" the connection will be ended on a
          tick when no data is transfered in the mean time. When
          "ax25 t3disc" is off, a RR(P) frame will be sent.
          On t3 = 0, the link will never be redundant. The value
          of t3 should NOT be under about 360 sec.
          Default: 900, range 0-3600
Timer 4:  Busy timeout
          Determines when a retry is sent when a RNR frame is
          received.
          Default: 60, range 1-600 (sec)
Timer 5:  Packet assembly timeout
          At timer tick, the remaining characters in the queue
          will be reassembled to a packet of PACLEN length.
          Default: 1, range 0-600 (sec)

ax25 t3disc
Syntax: ax25 t3disc <0|1>
When t3 ticks, the connection will be ended when no data is
transfered in the mean time. When t3disc is off, only a RR(P)
frame will be send.
Default: 1

isat
Syntax: isat <0|1>
Switch AT/386 mode off/on
Default: 0

editor
Syntax: editor [<filename>]
Searches the program /editor.exe and runs it WITHOUT LOADING the
command.com. The filename is as argument passed to the editor.
This editor must be a small text editor which runs too in an
environment with little memory space. The standard deivered
editor does so and is able to handle large files by loading them
part by part.

loadhi
Syntax: loadhi
This command is implemented for those -lucky ones- who own a
machine with XMS memory. NOS now looks for the program /loadhi
which ables the user to make a shell into the memory area between
640 k and 1 meg.

That should be most differences. Here is an added example
autoexec file:

# HRLNOS set-up-ing
# make sure to have at least the following files setup:
# between (): might be omitted; in CAPITALs: these are directories!
#  /hrlnos.exe           : HRLNOS exe file
#  /autoexec.nos         : HRLNOS setup file (this file)
#  /ftpusers             : with ftp user codes, passwords and directories
#                          see NOS_0618 manual by PA0GRI
#  /domain.txt           : with domain data (name to IP_addr translation)
# (/popusers)            : for pop mailbox access (see pop.doc)
# (/alias)               : for smtp mail aliasing (see bbs.doc)
#  /SPOOL
# (/SPOOL/rewrite)       : for smtp mail re-addressing (see bbs.doc)
# (/SPOOL/forward.bbs)   : for W0RLI-bbs forwarding (see bbs.doc)
# (/SPOOL/areas)         : with public mail areas in in (see bbs.doc)
#  /SPOOL/MQUEUE         : with outgoing mail in it
#  /SPOOL/MAIL           : with mail files in it
#  /SPOOL/HELP           : with 'host.hlp' as BBS welcome text;
#                          <bbs_command>.hlp (eg. area.hlp) for help in BBS
# (/SPOOL/SIGNATUR)      : with files username.sig containing mail signatures
# (/SPOOL/NEWS)          : for use by the NNTP client/server
# (/SPOOL/NEWS/JUNK)     : NNTP junk directory
# (/FINGER)              : with finger files (info), syntax <username.txt>
#
# don't forget to define a public FTP directory!
#
# Files, directories between brackets are OBGLIGED to be present.
# ATTENTION! All of the directory structure can be configurated dynamically
# with the "set" command or by changing the respective DOS environment
# variables. An example as used by pa3eug:
set tmp=n:\temp
set userfile=n:\
set hostfile=n:\
set maillog=n:\spool
set mailspool=n:\spool\mail
set mailqdir=n:\spool\mqueue
set routeqdir=n:\spool\mqueue
set alias=n:\
set dfile=n:\
set fdir=n:\finger
set arealist=n:\spool
set helpdir=n:\spool\help
set rewritefile=n:\spool
set popusers=n:\
set axroutefile=n:\spool
set arproutefile=n:\spool
set tz=utc-1
set forwardfile=n:\spool
NEVER USE THE AUTOEXEC.HRL AS IT IS!!! FIRST SETUP YOUR PARAMETERS, CALL, ETC!
exit
#
#
# Here are the actual setup commands.
# This was meant to be installed:
# two slip links "sl0" and "sl2" at com1 and com2
# two links from a SCC-card using the PE1CHL driver to the transmitters
# Because I'm not quite common with SCC-cards, I copied the SCC-parameters
# from someone else. They could be incorrect because I couldn't check it!
# Sometimes, the order of commands doen't seem to be too logic. My appolo-
# gied for that, but that's because this file is compiled from my own auto-
# exec-file... I wrote the comments later...
#
# Here we go....
#
# First let's set the 'fix' parameters. These will NEVER change during the
# use of the program. After the attachment of the interfaces you CANNOT change
# hostname, AX25 call and ip address!
domain suffix ampr.org.
hostname pa3eug.ampr.org
ip address [44.137.24.31]
ax25 mycall pa3eug
#
# Now we can define several ports:
attach asy 0x3f8 4 slip sl0 5000 256 2400
attach asy 0x2f8 3 slip sl2 5000 256 2400
attach scc 2 init 150 4 2 0 1 168 2 p4915200
attach scc 0 ax25 144 256 d1200
attach scc 2 ax25 430 256 d1200
#
# If we'd have a KISS-tnc, the attach-commands would be like this:
# attach asy 0x3f8 4 ax25 144 5000 256 4800
# attach asy 0x2f8 3 ax25 430 5000 256 4800
# The first line defines a 4800 bps link to a KISS TNC with interface name 144
# at COM1, the second line does the same for a line named 430 at COM2.
# 16550A-controllers are recognized automatically. Always use the combination
# "0x3f8 4" for COM1 and "0x2f8 3" for COM2.
#
# Now we defined a "way out", we can start several servers. We don't start
# NET/ROM because we don't like it, and because it's not implemented to save
# memory!
start ftp
start telnet
start ttylink
start smtp
start finger
start ax25
start remote
start nntp
start rip
start discard
start echo
start pop
#
# standard, routing goes to the 144 interface, further pa3eug-a goes to sl0
# and pi8tcp to sl2.
# It is NOT necessary to add full routing tables, because if a station onesn
# has connected, the route to him will be remembered, on AX25-level and at
# L3 (route and arp-result). This is done by the WANMPES and tcp/ip
# autorouter.
# For this propose, MINIHRL makes the axroute.dat and arproute.dat files.
# Don't panic if they're not present the first time you run the software...
# ALWAYS USE THE "route addprivate" command instead of just "route add"!
# Private routings will be skipped by the RIP router, if you DON'T the RIP
# network will go crazy because of all routings you SAY you have...
# (route add default doesn't need to be private...)
route add default 144
route addp pa3eug-a.ampr.org sl0
route addp pi8tcp sl2
#
# Whenever a CALL is trying to be connected without mentioning the interface,
# and without having a AX25 ROUTE entry (manual/automatic!), the CALL is
# considered to be at the 144 interface:
ax25 route add default 144
#
# events will be logged by NOS:
log \spool\nos.log
#
# Accept mailbox third-party mail and mbox attended is set OFF.
# One cannot use the "c" command in the mailbox to call the operator.
third on
mb atte off
#
# kiss setup:
# syntax is "param <int> <param> <param> <param> <.....>"
# The first parameter may be a KISS command. Here's a list of KISS commands:
# 1 : TXdelay (n x 10 ms)
# 2 : p-Persistance (256/(n+1))
# 3 : Slottime (n x 10 ms) (intervaltime between two attempts to sent on an
#                           occupied channel)
# 4 : TXtail (n x 10 ms)
# 5 : full duplex on/off  (0=off; 1=on)
# 6 : TNC dependant parameter (e.g. at the DTNC1: param 144 6 37 : set
#                              TNC to 4800 baud output speed)
# 255 : end KISS-mode
param 144 1 6
param 144 2 50
param 144 3 6
param 144 4 2
param 144 5 0
param 430 1 10
param 430 2 50
param 430 3 6
param 430 4 2
param 430 5 0
#
# Now some general set up.
#
# TCP RETRY gives the number of attempts to start a connection before a time
# out is generated. Whenever the (tcp/ip) connection is established, the
# number of retries will be multiplied by 3.
tcp retry 15
#
# attribute changes the status line into color or monochrome. Just try out
# and see what happens....
attr mono
#
# Here's the AX25 ID (broadcast) text. bct = broadcast text and
# bci = broadcast interval
# parameter ax t3disc makes a AX25-connection to be terminated at T3 tick.
# When set to "on", at mailbox login the following tekst will be shown:
# "inactivity time-out xx min." te zien.
ax bct "HRLNOS - PA3EUG"
ax bci 300
ax t3d off
#
# Here's the nntp (network news transfer protocol, poort 119) setup.
# This stands for itself. We ask pi8hrl for NNTP data:
nntp add pi8hrl 900 *
nntp profile fullname "Ram"n Kolb PA3EUG [44.137.24.31]"
nntp profile organ "AMPRNET Netherlands SUBNET East Brabant"
nntp profile reply [e-mail]
nntp profile sig /spool/signatur/sysop.sig
#
# Here's the smtp setup. Smtp timer will be well known. Smtp batch will put
# the HELO, MAIL FROM, RCPT TO and DATA lines in one packet.
smtp batch y
smtp ti 1800
#
# Now some stuff fot the mailbox. Mbox log logs every mailbox user to the
# file /spool/node.log; mbox mota sets the mailbox prompt. Mbox motd
# sets the mailbox message of the day.
mbox log y
mbox mota PA3EUG-HRLNOS v911211-2 <
mbox motd "Enter 'c' for a chat or '?' for a list of commands"
#
# Now set some remote control codes:
remote -s pa3eug
sysop 12345
# Here's the setup of the POP client:
# The mail is waiting at pi8hrl, and pi8hrl has (among others) in his
# /popusers file:
# py0yy:somebody:
# Pop mailhost sets pi8hrl as Post Office, and with mailbox the local mailfile
# is determined. Userdata makes the passwords go okay.
# (at pi8hrl the mailfile to be read is  /spool/mail/py0yy.txt)
pop mailhost pi8hrl
pop mailbox sysop
pop userdata py0yy somebody
#
# At last we make pi8hrl to be a domain server, and RIP routing goes to
# pi8hrl. After 5 minutes, we give up hope to reach the domain server...
dom ad pa3eug
dom tim 300
rip ad pa3eug 450
# This should be sufficient. Many mare things can be set up, but most of the
# parameters are okay of-their-own.
# Have a good luck, and send any questions/remarks to:
# [e-mail] OR [e-mail] OR
# PA3EUG @ ON4UBO.BLG.EU                                    ---73's, Ramon.